Skip to content

docs(extraction): pin GitHub source links to the 26.08.1 tag (NVBug 6628516) - #2579

Draft
kheiss-uwzoo wants to merge 3 commits into
NVIDIA:mainfrom
kheiss-uwzoo:docs/6628516-pin-github-refs-26.08
Draft

docs(extraction): pin GitHub source links to the 26.08.1 tag (NVBug 6628516)#2579
kheiss-uwzoo wants to merge 3 commits into
NVIDIA:mainfrom
kheiss-uwzoo:docs/6628516-pin-github-refs-26.08

Conversation

@kheiss-uwzoo

@kheiss-uwzoo kheiss-uwzoo commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Pin release-specific blob/main and tree/main GitHub links in versioned 26.08.1 extraction docs to the immutable 26.08.1 tag (Helm README/values, CLI, examples, source, nav, and redirects).
  • Leave contribution-policy links on main (contributing.md → CONTRIBUTING.md).
  • Fixes NVBug 6628516: after main advances, 26.08.1 readers no longer follow newer Helm keys, defaults, examples, or source.

Why this is on main

There is no 26.08.1 maintenance branch. Tag 26.08.1 currently matches upstream/main. This pin is for the 26.08.1 versioned docs snapshot.

After main diverges for the next train, restore /blob/main/ and /tree/main/ on main (or keep this pin only on a 26.08.1 branch) so latest docs stay evergreen.

Intentional leftovers

  • docs/docs/extraction/contributing.md still points at blob/main/CONTRIBUTING.md (evergreen, per bug expected result).
  • docs/docs/license.md still has four blob/main links (outside the extraction audit scope).
  • In-repo Helm/CLI markdown still contains blob/main self-links; this PR only changes published extraction docs and docs/mkdocs.yml.

Test plan

  • git grep for github.com/NVIDIA/NeMo-Retriever/(blob|tree)/main under docs/docs/extraction — only contributing.md remains
  • Sample 26.08.1 tag URLs resolve
  • Click Helm README, values.yaml, CLI, and example links from 26.08.1 release notes and deployment docs after publish
  • Confirm contribution links still open CONTRIBUTING.md on main

pre-draft: leakage, mkdocs --strict, ::a, ::p, ::r on the diff vs main

Base: upstream/main
Files: 21 extraction markdown pages and docs/mkdocs.yml (GitHub blob/tree pins to tag 26.08.1)

Check Result
Leakage (page roles + see [ CTAs) PASS — no see [ CTAs in changed markdown; faq/overview/multimodal-extraction have no nimOperator/nvcr.io/nim/installFfmpeg
Allowed paths PASS — 22 documentation files (extraction/*.md + mkdocs.yml)
mkdocs --strict PASS for this change — exit 1 from untracked leftover pages (custom-metadata.md, user-defined-stages.md), not this diff
::a audit PASS — pins target tag 26.08.1 (1992e3f); Helm README and CLI README exist at that tag; contributing.md remains blob/main/CONTRIBUTING.md
::p polish none needed — mechanical URL retarget from 26.08 to 26.08.1
::r style 95% — no blocking issues; no prose rewrite

Code drift (not in this docs PR): none for this pin.

PR: #2579

…8516)

Versioned 26.08 docs were sending readers to mutable main for Helm, CLI, examples, and source. Pin those references to the 26.08 release tag and keep contribution-policy links on main.
@kheiss-uwzoo kheiss-uwzoo self-assigned this Aug 24, 2026
@kheiss-uwzoo kheiss-uwzoo added 26.08 doc Improvements or additions to documentation 26.08.1 and removed 26.08 labels Aug 24, 2026
…628516)

Retarget the 26.08 blob/tree pins to the 26.08.1 release tag so versioned docs match the published train.
@kheiss-uwzoo kheiss-uwzoo changed the title docs(extraction): pin GitHub source links to the 26.08 tag (NVBug 6628516) docs(extraction): pin GitHub source links to the 26.08.1 tag (NVBug 6628516) Aug 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

26.08.1 doc Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant